feat: presence (keep phone notifications) + force delete + LID in calls#1
Open
adriano-rodrigues99 wants to merge 3 commits into
Open
feat: presence (keep phone notifications) + force delete + LID in calls#1adriano-rodrigues99 wants to merge 3 commits into
adriano-rodrigues99 wants to merge 3 commits into
Conversation
…er-compose.prod.yaml (cherry-pick de 98b7095, resolvido sobre maxpantech/develop: mantém o approach Multi-Device nativo do HEAD + markOnlineOnConnect:false + stopPresenceInterval no logout/close)
Allow bypassing cleanup errors during instance deletion with ?force=true query param, ensuring the database record is always removed even when logout or session cleanup fails.
Added logic to convert LID to phone number, improved error handling, and ensured call data integrity. This includes resolving pushName and caching mechanisms for better performance.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Presence + Force delete + LID em chamadas
Três ajustes do fork pessoal re-aplicados sobre o
developatual:1. Presença — manter notificações no celular do dono (
9fa78928)Device conectado via API se marcando como online/available faz o WhatsApp mutar o push no celular do dono. Mantém o device unavailable:
markOnlineOnConnect:false+ intervalo de presençaunavailable+stopPresenceIntervalno logout/close. (Preserva o approach Multi-Device nativo já existente no develop.)2. Force delete (
32c9cd83)Adiciona
?force=truenodeleteInstance(+forceDeleteInstanceno monitor + campoforceno dto). Combina com o delete resiliente que o upstream já tem: o caminho force bypassa oconnectionStatee remove a instância mesmo quando ela está tão quebrada que o delete normal estouraria (caso extremo não coberto pelo default).3. LID → telefone em chamadas (
c5f60350)O upstream resolve LID em chamadas com uma tentativa (
getPNForLID); se o mapping ainda não existe no signal store, a resposta de chamada (msgCall) falha. Esta versão adiciona cascata de 3 fallbacks:getPNForLID→ cacheisOnWhatsapp→ DBisOnWhatsapp.jidOptions. Relevante no MaxLav porque a maioria das ligações vem de números que já compraram (já estão noisOnWhatsapp), então o fallback acerta mesmo sem mapping no Baileys. Também: mantém ooriginalFromnorejectCall, resolvepushName, e enriquece o webhook (addressingMode/remoteJidAlt/isFinalEvent).eventProcessingQueueatual e preservando os blocosconnection.update/creds.update.Notas
developbuilda a imagem homolog.--no-verifypor erros de typecheck locais (deps não instaladas:fetch-socks, tipos do PrismaInstance/Message— client não gerado) — o CI com install completo valida.Refs maxpantech/workflow#1153